Replace leak sanitizer with mockalloc - #19
Draft
pflanze wants to merge 5 commits into
Draft
Conversation
Version from Github since the author has not released a new version.
I guess the problem is this limitation:
Allocations are tracked separately for each thread. This allows
tests to be run in parallel, but it means that the library will
report false positives if a pointer returned by an allocation on
one thread is later freed by a different thread.
Should be solvable by merging thread end states? (Needs custom TLS?)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is supposed to fix #17, just like #18 is.
Sadly, I again haven't succeeded in getting this to work, either. It is probably a limitation in the overly simplicistic mockalloc crate. I have an idea how to fix that, but that's for another time, too.
The nice thing about this crate would be that it is super low overhead and super cheap to compile, as well as super tiny and thus fully understandable. (But alloc-track (mentioned in #18) might be the more interesting of those two low-profile options.)